Conversation
jtschwar
pushed a commit
that referenced
this pull request
Jun 22, 2026
🤖 I have created a release *beep* *boop* --- ## [1.0.1](slabpick-v1.0.0...slabpick-v1.0.1) (2026-06-22) ### 🐞 Bug Fixes * properly set up release please ([#31](#31)) ([d236d66](d236d66)) * run names should be type str ([fe3aa58](fe3aa58)) * skip runs with missing voxel spacing in copick minislab generation ([7bceec1](7bceec1)) ### ⚙ Continuous Integration * set up release please for pypi ([#30](#30)) ([402db96](402db96)) --- Slabpick on PyPI. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Set up release-please for automated PyPI releases
Summary
release-please-config.jsonto configure automated release management with Python release type, changelog sections by conventional commit type, and initial version tracking.release-please-manifest.jsonseeding the package atv1.0.0pyproject.tomlfrom a hardcodedversion = "0.1.0"todynamic = ["version"]backed by[tool.hatch.version], sourcing the version fromsrc/slabpick/__init__.py__version__ = "1.0.0"tosrc/slabpick/__init__.pyas the single source of truth for the package versionNotes
Two fields in
release-please-config.jsonappear to be copied from a sibling project and need correcting before merge:"package-name"should be"slabpick", not"octopi""version-file"should be"src/slabpick/__init__.py", not"octopi/__init__.py"Test plan
.github/workflows/pip install -e .resolves version correctly viapython -c "import slabpick; print(slabpick.__version__)"main